v5.10.2

Compare Source

Today, we are issuing the 5.10.2 patch release.

Fix in Prisma CLI

• Invalid character error persists on 5.10.1 in Prisma Studio

v5.10.1

Compare Source

Today, we are issuing the 5.10.1 patch release.

Fix in Prisma Client / Prisma CLI

• Error: Invalid character when schema.prisma includes Chinese/Non-ASCII characters in a comment

v5.10.0

Compare Source

Today, we are excited to share the 5.10.0 stable release 🎉

🌟 Help us spread the word about Prisma by starring the repo ☝️ or posting on X about the release.

Highlights

Optimized relation queries in MySQL (Preview)

This release brings the optimizations for relation queries from the previous releases to MySQL as well! This means that by enabling the relationJoins Preview feature with the mysql database provider, you now also get access to the relationLoadStrategy option in relation queries that let you choose whether you want to merged relations on the application- or database-level.

If you enable the relationJoins Preview feature, you can choose between the join and query options:

• join (default): Sends a single query to the database and joins the data on the database-level.
• query: Sends multiple queries to the database and joins the data on the application-level.

To get started, enable the Preview feature in your Prisma schema:

// schema.prisma
generator client {
  provider        = "prisma-client-js"
  previewFeatures = ["relationJoins"]
}

Be sure to re-generate Prisma Client afterwards:

npx prisma generate

And finally, specify the relation loading strategy for your relation query via the relationLoadStrategy option as follows:

await prisma.user.findMany({
  relationLoadStrategy: 'join', // or 'query' 
  include: {
    posts: true,
  },
})

Note that in the example above, the relationLoadStrategy could be omitted altogether because join is used as the default value.

A few notes about relationLoadStrategy support on MySQL:

• relationLoadStrategy is supported for MySQL v8.0.14 and higher. MariaDB is not supported.
• Prisma ORM uses correlated sub-queries for MySQL (as opposed to LATERAL JOINs which are used on PostgreSQL).

Configure transaction options in the PrismaClient constructor

This feature enables you to configure the following transaction options on a global level via the PrismaClient constructor:

• isolationLevel: Sets the transaction isolation level. By default, this is set to the value currently configured in your database.
• timeout: The maximum amount of time the interactive transaction can run before being canceled and rolled back. The default value is 5 seconds.
• maxWait: The maximum amount of time Prisma Client will wait to acquire a transaction from the database. The default value is 2 seconds.

Here is an example of how you can set this value globally for all transactions:

const prisma = new PrismaClient({
  transactionOptions: {
    isolationLevel: 'ReadCommitted',
    timeout: 1_000, // 1 sec
    maxWait: 2_000  // 2 sec
  }
})

Thanks a lot to our fantastic community member @tockn, who took the initiative to implement this feature in Prisma ORM 🎉

Note that you can still override the global values by setting them on a particular transaction.

New P2037 code for “Too many database connections opened” errors

We introduced a new error code for “Too many database connections opened” errors: P2037. You can find all error codes in our documentation.

Access the Prisma Data Platform via Prisma CLI

Now available in Early Access, you can manage your workspace and configure Prisma Accelerate and Prisma Pulse directly from the terminal.

Visit our docs to learn more about the integration and try it out for yourself!

Fixes and improvements

Prisma Client

• called Option::unwrap() on a None value when using the relationJoins preview feature with driver adapters
• [5.9.0 Bug] Prisma.TransactionClient appears to be missing types
• Error after Upgrading from 5.8.1 to 5.9.0
• [5.9.0] @prisma/client in Next.js middleware
• [v5.9.0] $extends always return any
• Prisma edge runtime error
• [5.9.0] All queries result in any type
• Error: Prisma Client is unable to run in an edge runtime. As an alternative, try Accelerate: https://pris.ly/d/accelerate.
• [5.9.0] Error: Prisma Client is unable to run in an edge runtime. As an alternative, try Accelerate: https://pris.ly/d/accelerate.
• v5.9.0 / Don't generate type. And the error from the previous version is still there
• [5.9.0] Getting strange types after generating
• relationJoins: "The column t3.bookGenreTitle does not exist in the current database"
• Missing export @​prisma/client/generator-build
• relationJoins preview feature: called Option::unwrap() on a None value

v5.9.1

Compare Source

Today, we are issuing the 5.9.1 patch release.

Fixes in Prisma Client

In 5.9.0 we have changed our conditional exports in @prisma/client. This resulted in broken types for TypesScript users using certain combinations of module/moduleResolution settings. Additionally, it also caused a regression for Next.js users which have encountered invalid error messages from our side.

You can now try out 5.9.1 and let us know if you find a bug at https://pris.ly/prisma-prisma-bug-report

• [5.9.0] Getting strange types after generating #​22903
• v5.9.0 / Don't generate type. And the error from the previous version is still there #​22896
• [5.9.0] Error: Prisma Client is unable to run in an edge runtime. As an alternative, try Accelerate: https://pris.ly/d/accelerate. #​22893
• Error: Prisma Client is unable to run in an edge runtime. As an alternative, try Accelerate: https://pris.ly/d/accelerate. #​22889
• [5.9.0] All queries result in any type #​22888
• Prisma edge runtime error #​22886
• please how i cant fix this message issues #​22885
• [v5.9.0] $extends always return any #​22884
• [5.9.0] @​prisma/client in Next.js middleware #​22877
• Error after Upgrading from 5.8.1 to 5.9.0 #​22875
• [5.9.0 Bug] Prisma.TransactionClient appears to be missing types #​22870

Note: many issues are duplicates.

v5.9.0

Compare Source

Today, we are excited to share the 5.9.0 stable release 🎉 

🌟 Help us spread the word about Prisma by starring the repo ☝️ or posting on X about the release.

This release brings a number of small improvements as we continue our work on larger features which you will hear more about in the coming weeks:

• Improve the performance of relation queries by introducing JOINs (see last release).
• Support deployment to edge functions (already available in Early Access, you can apply for trying it out by taking our survey).

Highlights

Optimized result sets for more efficient queries

We continue our efforts of the performance of Prisma Client queries. In 5.1.0, we introduced the RETURNING keyword for several queries on PostrgeSQL and CockroachDB. We now expanded the use of RETURNING to SQLite and a broader range of queries for existing databases (e.g. delete on PostgreSQL and MongoDB). You can learn more about the optimizations of the result sets in these PRs:

• feat(qe): avoid extra select on delete queries
• feat(qe): enable queries with returning for sqlite

SQL Server: Return proper error for unreachable database

When trying migrate/introspect a SQL server instance that’s unreachable, Prisma ORM now returns the correct P1001 error instead of failing without an error. Learn more in this PR: SQL Server: Migrate/Introspection engine doesn't return P1001 error for unreachable url.

Fixes and improvements

Prisma Client

• Skip unnecessary select queries on create/update/delete
• .prisma/client: Name can't start with a dot
• Nested json is transformed to string when used “$type” key in object
• Parallel execution with Promise.all causes P2024 error in version 5.8.0 due to connection limit

Prisma Migrate

• SQL Server: Migrate/Introspection engine doesn't return P1001 error for unreachable url
• Prisma errors fetching table 'CHECK_CONSTRAINTS' (which only exists in MySQL 8.0.16+) in MySQL 8.0.14
• ERROR: column "..." being dropped, try again later when applying migrations with CRDB 23.1

Language tools (e.g. VS Code)

• Extension wrongfully suggests Json as a valid type completion on Sqlite

Company news

Test edge functions support in Early Access

Today, the only way how to use Prisma ORM in edge functions (e.g. Cloudflare Workers or Vercel Edge Functions) is by using Prisma Accelerate. However, we are actively working on making Prisma ORM compatible with edge functions natively as well. If you want to become an early tester, you can apply for the private Early Accessing program by taking this survey.

We Transitioned Prisma Accelerate to IPv6 Without Anyone Noticing

Last year, AWS announced the decision to begin charging for IPv4 addresses beginning in February 2024. This move had a major impact on Prisma Accelerate, prompting us to go all-in on IPv6. Learn more in this technical deep dive into how we approached our IPv6 migration, lessons learned, and the outcome for users of Prisma Accelerate.

Credits

Huge thanks to @​laplab, @​Druue, @​anuraaga, @​onichandame, @​LucianBuzzo, @​RobertCraigie, @​almeidx, @​victorgdb, @​tinola, @​sampolahtinen, @​AikoRamalho, @​petradonka for helping!

v5.8.1

Compare Source

Today, we are issuing the 5.8.1 patch release.

Fix in Prisma Client

• Parallel execution with Promise.all causes P2024 error in version 5.8.0 due to connection limit.

v5.8.0

Compare Source

🌟 Help us spread the word about Prisma by starring the repo or posting on X about the release. 🌟

Highlights

Happy New Year from your friends at Prisma! 🎊

In the last 4 weeks, we resolved some bugs on the ORM and made some progress on some exciting features that we’re not yet ready to announce. Stay tuned for the upcoming releases, in which we’ll be announcing new features. 😉

relationJoins improvements: Relation loading strategy per query (Preview)

In version 5.7.0, we released relationJoins into Preview. The relationJoins feature enables support for JOINs for relation queries.

This release adds support for the ability to specify the strategy used to fetch relational data per query when the Preview feature is enabled. This will enable you to choose the most efficient strategy for fetching relation data depending on your use case.

You can now load relation data using either of the following strategies:

• join — uses JOINs to fetch relation data
• query — uses separate queries to fetch relation data

When the relationJoins Preview feature is enabled, by default, the relation fetching strategy used is join. You can override the default behavior by using the relationLoadStrategy query option.

To get started, enable the Preview feature:

// schema.prisma
generator client {
  provider        = "prisma-client-js"
  previewFeatures = ["relationJoins"]
}

… and specify the relation loading strategy for your query as follows:

await prisma.user.findMany({
  relationLoadStrategy: 'query',
  include: {
    posts: true,
  },
})

Try it out and share your feedback and create a bug report if you encounter any issues.

Survey: Edge functions support

We’re working on bringing Edge function support to Prisma ORM and we would appreciate your input by submitting a response to our survey. By filling out the survey, you will be considered for our Early Access cohort as soon as we have something for you to try out.

Fixes and improvements

Prisma Client

• Log output of Node-API library engine is different
• target and timestamp are undefined in info events in Data Proxy client
• Wrong types of timestamp and duration in query events with Data Proxy
• Using citext fields with neon database driver causes conversion error
• Add FreeBSD 14 as a new platform
• PostgresError { code: "54023", message: "cannot pass more than 100 arguments to a function", severity: "ERROR", detail: None, column: None, hint: None }
• Int[] return as null

Prisma Migrate

• Prisma Migrate errors with Environment is non-interactive when VERCEL env var is defined

Language tools (e.g. VS Code)

• Add quickfix for Error validating field 'id' in model 'Post': MongoDB '@​default(auto())' fields must have 'ObjectId' native type.
• Append mention of update to "preview feature not known" error message

Credits

Huge thanks to @​anuraaga, @​onichandame, @​LucianBuzzo, @​RobertCraigie, @​fqazi, @​KhooHaoYit, @​alencardc, @​Oreilles, @​tinola, @​AikoRamalho, @​luxaritas for helping!

Company news

🎉 A billion queries and counting: Prisma Accelerate

Prisma Accelerate, our global database cache has served over 1 billion queries since its General Availability launch.

We’d like to give a shoutout to our team and everyone who’s been with us on this journey. Stay tuned for some exciting products and features in the pipeline for 2024!

🔮 Prisma ORM Ecosystem

Are you building a cool tool, extension, generator, CLI tool or anything else, for Prisma ORM? Let us know.

We would like to learn about it and feature it on our Ecosystem page.

💼 We’re hiring

If you're interested in joining our growing team to help empower developers to build data-intensive applications, Prisma is the place for you. Check out our Careers page for open positions.